Method and apparatus for displaying embedded chip states and embedded chip end-user application states

ABSTRACT

A method and apparatus for managing applications installed on a smartcard. The invention comprises a Smartcard Management Program (SMP), a User Action Program (UAP), a User Command Program (UCP), an Application Status Update Program (ASUP), and a Card Status Update Program (CSUP). The SMP interfaces with smartcard communications system and accepts the user commands. The UAP obtains applications from external sources, updates the user profile, and transmits the user profile to the user for viewing on a graphical user interface. The UCP breaks the user commands into card actions and application actions and executes the card actions and application actions. The ASUP updates the user profile by changing the entry in an application name column, an application status column, a user action column, and an information column. The CSUP updates the user profile by changing the entry in the card status field.

CROSS-REFERENCE TO RELATED APPLICATION

[0001] The subject matter of the present application is related to U.S.patent application Ser. No. ______, attorney docket numberAUS920030090US1, and U.S. patent application Ser. No. ______, attorneydocket number AUS920030093, incorporated herein by reference.

FIELD OF THE INVENTION

[0002] The present invention is related generally to the organization offinancial accounts. Specifically, the present invention is directedtowards a method of managing smartcard applications.

BACKGROUND OF THE INVENTION

[0003] The use of credit cards in consumer transactions is well known inthe art. A credit card is defined as an account card issued by aspecific bank or financial institution for the purpose of purchasinggoods and services on credit provided by the bank or financialinstitution. Credit cards typically have a preset spending limit andspecific terms regarding payment terms, interest rates, grace periods,and other terms and conditions. However, the credit card itself does notcontain any information other than the account number. In order tocomplete a transaction, the credit card account number is read from thecard, sent to the bank or financial institution for verification ofaccount and charge authorization, and returned to the vendor withapproval for the transaction to proceed. The transaction process can betime consuming when the transaction occurs during peak purchasingperiods or when the transaction takes place in a foreign country. Thetransaction may be stopped entirely if the vendor is unable to establishcommunications with the bank. Moreover, credit cards apply to a singleaccount. In other words, the bank or financial institution must issueone credit card to the consumer for every account, requiring theconsumer to carry multiple credit cards when the consumer has more thanone account. Therefore, a need exists for a credit card that can be usedfor multiple accounts.

[0004] Debit cards are also well known in the art. With a debit card theconsumer spends money already deposited in an account, rather thancreating a credit account that will be paid at some later time. Debitcards are frequently used with deposit accounts such as checking,savings, and money market accounts. Unfortunately, like credit cards,debit cards card only contain a single account number. The vendor muststill authorize the transaction through a communications network inorder for the transaction to proceed, and the debit card can only beused for transactions with a single account. Therefore, a need existsfor a debit card that can be used for multiple accounts.

[0005] A smartcard is one solution to the problems encountered withtraditional credit and debit cards. A smartcard is a card, sizedsimilarly to a credit card, which contains a processor and a memory. Asmartcard is more advantageous than a credit card in that the smartcardcan store and update account information within the smartcard memory.Storing and updating the account information within the smartcard memoryis advantageous because charge authorization can be obtained directlyfrom the card itself rather than through communications with the bank orfinancial institution. Moreover, because the smartcard has the abilityto store and update information, one smartcard can contain informationregarding a plurality of accounts. The ability of the smartcard to storeaccount information on a plurality of accounts eliminates the need forthe consumer to carry a plurality of cards. Instead, the consumer cancarry one smartcard that contains account information for the user'schecking, savings, money market, and credit accounts.

[0006] Moreover, smartcards contain additional flexibility because auser can add various applications onto their smartcard. One example ofan application for a smartcard is a health care application. In a healthcare application, a smartcard may contain the user's heath insuranceinformation so that the user's doctor can scan the smartcard and receivethe patient's updated medical and insurance information, therebystreamlining the information exchange between the doctor, the patient,and the insurer. A similar application can be added to the smartcard forprescription drugs so that the doctor can use the card to know thestatus of the user's prescriptions.

[0007] Another example of an application is an airline frequent flyerapplication. In the frequent flyer application, the smartcard containsthe user's frequent flyer information such as the account number,mileage balance, status level, and so forth. When the user purchases airtravel with the smartcard, the frequent flyer information isautomatically connected to the travel information, streamlining theexchange of information between the user and the airline.

[0008] However, the combination of a plurality of accounts andapplications on a single smartcard creates new problems that were notpreviously encountered with credit or debit cards. One of these problemsis efficient organization and maintenance of the accounts andapplications on the smartcard. Smartcard users need to be able to add,modify, update, and delete accounts and applications as needed.Therefore, a need exists for an efficient method of organizing andmaintaining accounts and applications associated with a smartcard.

[0009] The problem of smartcard management has been addressed by theprior art. U.S. Pat. No. 5,544,246 (the '246 patent) entitled “SmartcardAdapted for a Plurality of Service Providers and for Remote Installationof Same” discloses a method of organizing and limiting access to thefiles installed within a smartcard. U.S. Pat. No. 6,199,762 B1 (the '762patent) entitled “Methods and Apparatus for Dynamic SmartcardSynchronization and Personalization” discloses an account maintenancesystem for a smartcard. What is needed beyond the '246 patent and the'762 patent is a method for organizing a plurality of accounts andapplications associated with a smartcard.

[0010] Consequently, a need exists in the art for a method fororganizing accounts and applications associated with a smartcard.Furthermore, a need exists for a method for adding, deleting, updating,and modifying accounts and applications associated with a smartcard. Theneed extends to an apparatus for implementing the aforementionedmethods.

SUMMARY OF THE INVENTION

[0011] The present invention, which meets the needs identified above, isa method and apparatus for managing applications installed on asmartcard. The present invention can be embodied in a software programoperable on a computer. In the software embodiment, the inventioncomprises a Smartcard Management Program (SMP), a User Action Program(UAP), a User Command Program (UCP), an Application Status UpdateProgram (ASUP), and a Card Status Update Program (CSUP). The SMPinterfaces with smartcard communications system and accepts the usercommands. The UAP obtains applications from external sources, updatesthe user profile, and transmits the user profile to the user for viewingon a graphical user interface (GUI).

[0012] The UCP breaks the user commands into card actions andapplication actions and executes the card actions and applicationactions. Possible card actions include updating the PIN. Possibleapplication actions include adding, installing, personalizing, updating,and deleting an application.

[0013] The ASUP updates the user profile by changing the entry in anapplication name column, an application status column, a user actioncolumn, and an information column. Possible application states includewithout limitation: new, downloaded, installed, ready, update available,blocked, unblocked and personalized. An application is new when theapplication is available to the user. An application is downloaded whenthe user has downloaded the compressed data file for the application tothe smartcard. An application is installed when the user has installedthe compressed data file. An application is personalized when it hasbeen properly set up by the user, possibly including registration. Anapplication is ready when it is ready to be used. An application has anupdate available when there is a downloadable update available for theapplication. An application is blocked when the application issuer orthe smartcard issuer has temporarily blocked the application. Anapplication issuer or smart card issuer can also unblock an application.

[0014] The CSUP updates the user profile by changing the entry in thecard status field. Possible card states include without limitation:terminated, updated PIN, and locked. The card is terminated when thesmartcard issuer blocks all activity on the smartcard, such as when thesmartcard is lost or stolen. The PIN needs to be updated when thesmartcard issuer resets the PIN, possibly for security reasons. The cardis locked when the smartcard issuer wants to temporarily block activityon the smartcard, possibly to affirm that the activity on the card isnot fraudulent.

BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The novel features believed characteristic of the invention areset forth in the appended claims. The invention itself, however, as wellas a preferred mode of use, further objectives and advantages thereof,will best be understood by reference to the following detaileddescription of an illustrative embodiment when read in conjunction withthe accompanying drawings, wherein:

[0016]FIG. 1 is an illustration of the communications system associatedwith a smartcard;

[0017]FIG. 2 is an illustration of the flow of information between thesmartcard, the chip management system (CMS), and the client card system(CCS);

[0018]FIG. 3 is an illustration of the flow of information between thesmartcard user, the CMS, an external server, and the CSS;

[0019]FIG. 4 is an illustration of a computer memory containing thecomputer program embodiment of the present invention;

[0020]FIG. 5 is a flowchart of the logic of the Smartcard ManagementProgram (SMP) of the present invention;

[0021]FIG. 6 is a flowchart of the logic of the User Action Program(UAP) of the present invention;

[0022]FIG. 7 is a flowchart of the logic of the User Command Program(UCP) of the present invention;

[0023]FIG. 8 is a flowchart of the Application Status Update Program(ASUP) of the present invention;

[0024]FIG. 9 is a flowchart of the Card Status Update Program (CSUP) ofthe present invention; and

[0025]FIG. 10 is an illustration of the display of the graphical userinterface (GUI) on the CSS associated with the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

[0026] “Application issuer” shall have the same meaning herein as theterm “Application Provider” (AP).

[0027] “Chip” means a processor and a memory contained within a smartcard wherein the processor is connected to the memory and is capable ofwired or wireless communication with a card reader or cardreader/writer.

[0028] “Chip Information Number” (CIN) means a unique number assigned toeach individual chip. The CIN can be used to identify the correctsmartcard user when used in conjunction with a PIN.

[0029] “Chip Management System” (CMS) means a system that manages thelifecycle of the chip including without limitation storage andmanagement of a card profile associated with a chipholder.

[0030] “Client Card System” means a computer having an interface forcommunication with a smart card.

[0031] “Computer” means a machine having a processor, a memory, and anoperating system, capable of interaction with a user or other computer,and shall include without limitation: desktop computers, notebookcomputers, servers, personal digital assistants (PDAs), handheldcomputers, and cell phones.

[0032] “Display” means a visual depiction of a web page or computerprogram on a graphical user interface (GUI).

[0033] “Distribution Server” (DS) means a server that is a trusted nodeto the CMS that can obtain the chipholder profile from the CMS andpackage information from the chipholder profile into ApplicationProtocol Data Units (APDU). The DS has an Intelligent Gateway mode wherethe user is directly interfacing with the server or a router mode whereanother device such as an automatic teller machine (ATM) is performingthe interaction with the user.

[0034] “Input device” means a keyboard, mouse, trackball, touchpad,touchpoint device, stylus pen, touch screen, or any other type of deviceused to input data into a computer.

[0035] “Post-issuance data” means instructions and data for adding,modifying, or deleting data stored in a chip. One type of post issuancedata is a user profile.

[0036] “Personal Information Number” (PIN) means a unique numberassigned to each individual smartcard. The PIN can be used to identifythe correct smartcard user when used in conjunction with a CIN.

[0037] “Security Server” (SS) means a server that provides for securetransmission of data from the CMS to the DS.

[0038] “Smartcard” means a card used for personal or businesstransactions comprising at least a processor and a memory capable ofsupporting an operating system, application programs, storage of chipholder personalization data, application data and other data as may berequired by the issuer of a smart card.

[0039] “User interaction” means activating a button on a display byclicking on the button with a user input device or by touching thescreen with a human hand or object; or activating a menu item on adisplay by clicking on the item with a user input device or by touchingthe screen with a human hand or object.

[0040]FIG. 1 is a diagram of one embodiment of a system 20 for carryingout operations associated with and providing post-issuance data tosmartcard 32. Smartcard 32 is shown inserted into client card system(CSS) 30. CSS 30 may be, for example, a point-of-sale terminal, anautomatic teller machine (ATM), or similar device. In general, smartcard32 is capable of communicating with CSS 32. For example, smartcard 32may have a set of electrically conductive contacts arranged on asurface, and CSS 30 may have a similarly arranged set of electricallyconductive contacts located in a smart card interface. When smartcard 32is inserted into CSS 30, corresponding members of the two sets ofcontacts may come into physical contact with one another. In addition,smartcard 32 is preferably capable of establishing and carrying outsecure communications with CSS 30 as described in U.S. patentapplication Ser. No. ______ (attorney docket number AUS920030090).

[0041] In addition to CSS 30 and smartcard 32, system 20 also includeschip management system (CMS) 22, security server (SS) 24, distributionserver (DS) 28, and communication network 26. As indicated in FIG. 1,CSS 30, CMS 22, SS 24, and DS 28 are connected to communication network26. Communication network 26 includes, without limitation, the publicswitched telephone network (PSTN) and/or the Internet. CSS 30, CMS 22,SS 24, and DS 28 communicate with one another via communication network26 to convey post-issuance data to smartcard 32 via a securecommunication channel established within communication network 26.

[0042] One type of post-issuance data is the user profile describedherein. FIG. 2 is an illustration of the process of CSS 30 obtaininguser profile 40 from CMS 22. FIG. 2 is best understood when viewed inconjunction with Smartcard Management Program (SMP) 100 in FIG. 5. Whensmartcard 32 is inserted into CSS 30, CSS 30 reads CIN 34 from smartcard32. CSS 30 then transmits CIN 34 to CMS 22. CMS 22 uses CIN 34 to accessthe user's profile 40. CMS 40 then transmits user profile 40 back to CSS30, where CSS 30 displays user profile 40 on graphical user interface(GUI) 42. Display 600 in FIG. 10 is one possible illustration of thedisplay of GUI 42.

[0043] As part of the present invention, the smartcard user can modifyhis user profile from any CSS. FIG. 3 is an illustration of the processof a user 46 modifying his user profile 40. FIG. 2 is best understoodwhen viewed in conjunction with User Action Program (UAP) 200 in FIG. 6.User 46 views his user profile on GUI 42. User 46 then performs a useraction on a input device 44. CSS 30 transforms the user action into anelectronic user command and transmits the user command to CMS 22. CMS 22uses the user command to modify user profile 40. If necessary, CMS 22can send a request to external server 48 and external server 48 willsend an application, an update, or similar data back to CMS 22. CMS 22then sends the updated user profile back to CSS 30, where CSS 30displays the updated user profile on GUI 42. This process illustrated inFIG. 3 ends when smartcard 32 is removed into CSS 30 or user 46terminates the process by input into input device 44. Alternatively, theuser profile can be installed on the smartcard and updates sent to auser profile archive in the CMS.

[0044] The internal configuration of a computer, including connectionand orientation of the processor, memory, and input/output devices, iswell known in the art. The present invention is a methodology that canbe embodied in a computer program. Referring to FIG. 4, the methodologyof the present invention is implemented on software by SmartcardManagement Program (SMP) 100. SMP 100 comprises User Action Program(UAP) 200, User Command Program (UCP) 300, Application Status UpdateProgram (ASUP) 400, and Card Status Update Program (CSUP) 500. SMP 100,UAP 200, UCP 300, ASUP 400, and CSUP 500 described herein can be storedwithin the memory of a computer on CMS 22, SS 24, DS 28, or the CSS 30depicted in FIGS. 1, 2, and 3. Alternatively, SMP 100, UAP 200, UCP 300,ASUP 400, and/or CSUP 500 can be stored in an external storage devicesuch as a removable disk or a CD-ROM. Memory 98 is illustrative of thememory within CMS 22 of FIGS. 1, 2, and 3. Memory 92 also contains userprofile 40. The present invention may interface with user profile 40through memory 98. As part of the present invention, the memory 98 canbe configured with SMP 100, UAP 200, UCP 300, ASUP 400, and/or CSUP 500.

[0045] In alternative embodiments, SMP 100, UAP 200, UCP 300, ASUP 400,and/or CSUP 500 can be stored in the memory of other computers. Thisconfiguration allows the processor workload to be distributed across aplurality of processors instead of a single processor. Furtherconfigurations of SMP 100, UAP 200, UCP 300, ASUP 400, and/or CSUP 500across various memories are known by persons skilled in the art.

[0046] Turning to FIG. 5, a flowchart of the logic of SMP 100 isillustrated. SMP 100 is a program which runs while the smartcard isinserted into a CSS. SMP 100 starts (102) when the user inserts thesmartcard into the CSS (104). Generally, the user must enter his PIN onthe input device on the CSS in conjunction with inserting the smartcardinto the CSS. The CSS then reads the CIN from the smartcard andtransmits the CIN to the CMS (106). The CMS then uses the CIN to accessthe user profile (108). The CMS then transmits the user profile back tothe CSS (110). The CSS then displays the user profile on the GUI (112).SMP 100 then makes a determination whether there is a user command(114). If there is a user command, SMP 100 runs UAP 200 (116) andreturns to step 114. If at step 114 there is not a user command (i.e.the user has removed his smartcard from the CSS), SMP 100 ends (118).

[0047] Turning to FIG. 6, a flowchart of the logic of UAP 200 isillustrated. UAP 200 starts (202) when prompted by SMP 100. UAP 200accepts the user command entered in SMP 100 (204) and directs the CSS totransmit the user command to the CMS (206). UAP 200 then makes adetermination whether an application is available from an externalsource (208). If an application is available from an external source,UAP 200 obtains the application from the external source (210) andproceeds to step 212. If at step 208 an application is not availablefrom an external source, UAP 200 proceeds directly to step 212. At step212, UAP 200 runs UCP 300 (212). UAP 200 then runs ASUP 400 (214) andCSUP 500 (216). UAP 200 then directs the CMS to send the updated userprofile to the CSS (218). The CSS then displays the updated user profileon the GUI (220). UAP 200 then ends (222).

[0048] Turning to FIG. 7, a flowchart of the logic of UCP 300 isillustrated. UCP 300 starts (302) when prompted by UAP 200. UCP 300accepts the user command entered in SMP 100 (304). UCP 300 then makes adetermination whether the user command is a card action or anapplication action (306). In other words, UCP 300 classifies usercommands into commands concerning applications installed on the card andcommands concerning the smartcard itself. If the command is a cardaction, then UCP 300 makes a determination whether the card action is auser command to update the PIN (308). If the user does not want toupdate the PIN, UCP 300 returns to step 306. If the user wants to updatethe PIN, the UCP 300 allows the user to update the PIN (310) andproceeds to step 332. Persons skilled in the art are aware of other cardactions in addition to updating a PIN.

[0049] Returning to step 306, if the user command is an applicationaction, then UCP 300 proceeds to step 312 where UCP 300 makes adetermination whether the user command is to add an application (312).If the user command is to add an application, then UCP 300 adds theapplication to the user profile (314) and proceeds to step 332. Inadding the application to the user profile, UCP 300 downloads thecompressed application data file to the user profile and/or smartcardand adds the application name to the application name column (see FIG.10). Returning to step 312, if the user does not want to add anapplication, UCP 300 proceeds to step 316 where UCP 300 makes adetermination whether the user command is to install an application(316). If the user command is to install an application, UCP 300installs the application (318) and proceeds to step 332. In installingthe application, UCP 300 decompresses the compressed application datafile and runs the install program associated with the application.Returning to step 316, if the user does not want to install anapplication, USP 300 proceeds to step 320 where UCP 300 makes adetermination whether the user command is to personalize an application(320). If the user wants to personalize an application, then UCP 300personalizes the application selected by the user (322) and proceeds tostep 332. In personalizing the application, the user adds any necessaryor optional data to the application to place the application in a stateto perform a task. Personalizing an application can include registeringthe application.

[0050] Returning to step 320, if the user does not want to personalizethe application, then UCP 300 makes a determination whether the usercommand is to update an application (324). If the user wants to updatean application, then UCP 300 downloads the update from the applicablelocation, installs the update (326), and proceeds to step 332. Returningto step 324, if the user does not want to update the application, UCP300 makes a determination whether the user wants to delete theapplication (328). If the user does not want to delete the application,UCP 300 returns to step 312. If the user wants to delete theapplication, UCP 300 deletes the application from the user profile (330)and proceeds to step 332. In deleting the application, UCP 300 removesthe application from the user profile and/or the smartcard. Personsskilled in the art are aware of how to add, install, personalize,update, and delete an application from a smartcard and/or user profile.Persons skilled in the art are also aware of other application actionsbesides the ones described in steps 312 through 330. UCP 300 thenupdates the user profile (332) and ends (334).

[0051] Turning to FIG. 8, a flowchart of the logic of ASUP 400 isillustrated. ASUP 400 starts (402) when prompted by UAP 200. ASUP 400uses the CIN to access the user profile (404). ASUP 400 then makes adetermination whether there are any applications that can be installedon the user profile which are not already installed (406). If there arenot any applications that can be installed on the user profile, ASUP 400proceeds directly to step 414. If there are applications which can beinstalled, ASUP 400 adds the application name column of the user profile(see FIG. 10) (408). ASUP 400 then adds the “new” icon to theapplication status column (see FIG. 10) (410). ASUP 400 then adds the“download” button to the user actions column (see FIG. 10) (412). ASUP400 then proceeds to step 414.

[0052] At step 414, ASUP 400 makes a determination whether anyapplications are saved on the user profile (414). If there are not anyapplications saved on the user profile, ASUP 400 proceeds to step 454.If there are applications saved on the user profile, ASUP 400 goes tothe first application and makes a determination whether the applicationis downloaded (416). If the application is downloaded, ASUP 400 removesthe “new” icon from the application status column and adds the“downloaded” icon to the application status column (418). ASUP 400 thenremoves the “download” button from the user action column and adds the“install” and “delete” buttons to the user action column (420). ASUP 400then proceeds to step 422.

[0053] Returning to step 416, if the application is not downloaded, thenASUP 400 proceeds to step 422 where ASUP 400 makes a determinationwhether the application is installed (422). If the application isinstalled, ASUP 400 removes the “downloaded” icon from the applicationstatus column and adds the “installed” icon to the application statuscolumn (424). ASUP 400 then removes the “install” button from the useraction column and adds the “personalize” button to the user actioncolumn (426). ASUP 400 then proceeds to step 428.

[0054] Returning to step 422, if the application is not installed, thenASUP 400 proceeds to step 428 where ASUP 400 makes a determinationwhether the application is personalized (428). If the application ispersonalized, ASUP 400 removes the “installed” icon from the applicationstatus column and adds the “ready” icon to the application status column(430). ASUP 400 then removes the “personalize” button from the useraction column (432). ASUP 400 then proceeds to step 434.

[0055] Returning to step 428, if the application is not personalized,then ASUP 400 proceeds to step 434 where ASUP 400 makes a determinationwhether an update for the application is available (434). If an updatefor the application is available, ASUP 400 adds the “update available”icon to the application status column (436). ASUP 400 then adds the“update” button to the user action column (438). ASUP 400 then proceedsto step 440.

[0056] Returning to step 434, if an update for the application is notavailable, ASUP 400 proceeds to step 440 where ASUP 400 makes adetermination whether the application is blocked (440). An applicationis blocked if the application issuer has stopped the user from using theparticular application. Persons skilled in the art are aware of how toblock an application on a smartcard. If the application is blocked, ASUP400 adds the “blocked” icon to the application status column (442). ASUP400 then hides the buttons in the user action column (444). ASUP 400then proceeds to step 450.

[0057] Returning to step 440, if the application is not blocked, ASUP400 proceeds to step 446 where ASUP 400 makes a determination whetherthe “blocked” icon is in the application status column (446). If the“blocked” icon is not in the application status column, ASUP 400proceeds to step 450. If the “blocked” icon is in the application statuscolumn, ASUP 400 removes the “blocked” icon from the application statuscolumn and displays the user action buttons (448). ASUP 400 thenproceeds to step 450.

[0058] At step 450, ASUP 400 makes a determination whether there isanother application on the user profile (450). If there is anotherapplication on the user profile, ASUP 400 goes to the next application(452) and returns to step 416. If at step 450 there is not anotherapplication, ASUP 400 updates the user profile (454) and ends (456).

[0059] Turning to FIG. 9, a flowchart of the logic of CSUP 500 isillustrated. CSUP 500 starts (502) when prompted by UAP 200. CSUP 500then uses the CIN to access the user profile (504). CSUP 500 then makesa determination whether the smartcard has been terminated (506). Asmartcard has been terminated if the smartcard issuer has blocked allactivity on the smartcard. A smartcard may be terminated if thesmartcard is lost or stolen. Persons skilled in the art are aware of howto terminate a smartcard. If the smartcard has been terminated, CSUP 500changes the card status to “card terminated” (508) and proceeds to step520. If at step 506 the card has not been terminated, CSUP 500 makes adetermination whether the PIN has been reset (510). A PIN has been resetwhen the smartcard issuer deletes an old PIN and requests that the userset a new PIN. Persons skilled in the art are aware of how to reset aPIN. If the PIN has been reset, CSUP 500 changes the card status to“update PIN” (512) and proceeds to step 520. If at step 510 the PIN hasnot been reset, CSUP 500 makes a determination whether the card islocked (514). A card is locked if the smartcard issuer wants totemporarily block the use of the card, but not terminate the card.Persons skilled in the art are aware of how to lock a smartcard. If thecard is locked, CSUP 500 changes the card status to “card locked—callcustomer service for more information” (516) and proceeds to step 520.If at step 514 the card is not locked, CSUP 500 changes the card statusto “ready” (518) and proceeds to step 520. At step 520, CSUP 500 updatesthe user profile (520) and ends (522).

[0060]FIG. 10 is one possible display 600 from GUI 42 depicted in FIGS.2 and 3. Display 600 depicts the card status 602, which is modified byCSUP 500 in FIG. 9. Display 600 also depicts numerous applications 604which can be modified by UCP 300 depicted in FIG. 7 and ASUP 400depicted in FIG. 8. ASUP 400 makes reference to application name column606, application status column 608, user action column 610, all of whichare depicted in display 600. Display 600 also contains informationcolumn 612 which displays any additional information related to aparticular application 604.

[0061] While the disclosed application for the present invention iswithin smartcards, this disclosure is not meant to be limiting in anyway. The present invention can be alternatively embodied in wirelessdevices, home appliances, and the like. In fact, the present inventionis advantageous whenever there is a need to organize various kinds ofinformation.

[0062] With respect to the above description, it is to be realized thatthe optimum dimensional relationships for the parts of the invention, toinclude variations in size, materials, shape, form, function and mannerof operation, assembly and use, are deemed readily apparent and obviousto one skilled in the art, and all equivalent relationships to thoseillustrated in the drawings and described in the specification areintended to be encompassed by the present invention. The novel spirit ofthe present invention is still embodied by reordering or deleting someof the steps contained in this disclosure. The spirit of the inventionis not meant to be limited in any way except by proper construction ofthe following claims.

What is claimed is:
 1. A method for managing a plurality of applicationscomprising: obtaining a chipholder identification number from a memory;using the chipholder identification number to obtain a user profile;transmitting the user profile to a graphical user interface; anddisplaying data contained within the user profile on the graphical userinterface.
 2. The method of claim 1 further comprising: accepting acommand to add an application to the user profile; and adding anapplication to the user profile.
 3. The method of claim 1 furthercomprising: accepting a command to delete an application from the userprofile; and deleting an application from the user profile.
 4. Themethod of claim 1 further comprising: accepting a command to install anapplication on the user profile; and installing an application on theuser profile.
 5. The method of claim 1 further comprising: accepting acommand to personalize an application on the user profile; andpersonalizing an application on the user profile.
 6. The method of claim1 further comprising: accepting a command to download an application tothe user profile; and downloading an application to the user profile. 7.The method of claim 1 further comprising: accepting a command to updatean application on the user profile; and updating an application on theuser profile.
 8. The method of claim 1 further comprising: accepting acommand to block an application on the user profile; and blocking anapplication on the user profile.
 9. The method of claim 1 wherein thememory is located on a smartcard.
 10. The method of claim 9 furthercomprising: accepting a command to terminate the smartcard; andterminating the smartcard.
 11. The method of claim 9 further comprising:accepting a command to lock the smartcard; and locking the smartcard.12. The method of claim 1 further comprising: accepting a command toreset a PIN; and resetting the PIN.
 13. The method of claim 1 whereinthe memory is located on a wireless device.
 14. The memory of claim 1wherein the memory is located on an appliance.
 15. A program productoperable on a computer, said program product comprising: a computerusable medium; wherein the computer usable medium comprises instructionscomprising: instructions for obtaining a chipholder identificationnumber from a memory; instructions for using the chipholderidentification number to obtain a user profile; instructions fortransmitting the user profile to a graphical user interface; andinstructions for displaying data contained within the user profile onthe graphical user interface.
 16. The program product of claim 15further comprising: instructions for accepting a command to add anapplication to the user profile; and instructions for adding anapplication to the user profile.
 17. The program product of claim 15further comprising: instructions for accepting a command to delete anapplication from the user profile; and instructions for deleting anapplication from the user profile.
 18. The program product of claim 15further comprising: instructions for accepting a command to install anapplication on the user profile; and installing an application on theuser profile.
 19. The program product of claim 15 further comprising:instructions for accepting a command to personalize an application onthe user profile; and instructions for personalizing an application onthe user profile.
 20. The program product of claim 15 furthercomprising: instructions for accepting a command to download anapplication to the user profile; and instructions for downloading anapplication to the user profile.
 21. The program product of claim 15further comprising: instructions for accepting a command to update anapplication on the user profile; and instructions for updating anapplication on the user profile.
 22. The program product of claim 15further comprising: instructions for accepting a command to block anapplication on the user profile; and instructions for blocking anapplication on the user profile.
 23. The program product of claim 15wherein the memory is located on a smartcard.
 24. The program product ofclaim 23 further comprising: instructions for accepting a command toterminate the smartcard; and instructions for terminating the smartcard.25. The program product of claim 23 further comprising: instructions forlocking the smartcard.
 26. The program product of claim 23 furthercomprising: instructions for locking the smartcard.
 27. The programproduct of claim 23 further comprising: instructions for resetting aPIN.
 28. The program product of claim 15 wherein the memory is locatedon a wireless device.
 29. The program product of claim 15 wherein thememory is located on an appliance.
 30. A program product operable on acomputer, said program product comprising: a computer usable medium; asmartcard management program installed on the computer readable medium;and wherein the smartcard management program allows a user to manage aplurality of applications on a smartcard.
 31. The program product ofclaim 30 wherein said smartcard management program accesses a userprofile based on a chipholder identification number.
 32. The programproduct of claim 30 wherein said smartcard management program furthercomprises: a user action program; and wherein the user action programtransmits a user profile to a graphical user interface.
 33. The programproduct of claim 30 wherein said smartcard management program furthercomprises: a user command program; and wherein the user command programexecutes a user command.
 34. The program product of claim 30 whereinsaid smartcard management program further comprises: an applicationstatus update program; and wherein the application status update programupdates an application name, application status, an application useraction, or an application information for one of the applications. 35.The program product of claim 30 wherein said smartcard managementprogram further comprises: a card status update program; and wherein thecard status update program updates a status of the smartcard.
 36. Theprogram product of claim of claim 33 wherein the user command is to addan application.
 37. The program product of claim of claim 33 wherein theuser command is to delete an application.
 38. The program product ofclaim of claim 33 wherein the user command is to update an application.39. The program product of claim of claim 33 wherein the user command isto download an application.
 40. The program product of claim of claim 33wherein the user command is to install an application.
 41. The programproduct of claim of claim 33 wherein the user command is to personalizean application.
 42. The program product of claim of claim 33 wherein theuser command is to update an application.